Easy creation of mobile code

ABSTRACT

A user is presented with a first display with certain parties and a second display on the same screen, where the user can drag and drop the parties on the first screen to the second screen to create a desired network flow. A service provider, such as a payment provider, builds code based on the network flow and zips it into a downloadable file. The user can then easily implement the zipped code into a mobile app that will allow a user to send data through the app using the payment provider. The zipped code uses a library of data options offered by the payment provider and allows the user to input custom variables into these options. Code is automatically generated for the user to use based on the user input.

CROSS REFERENCE TO RELATED APPLICATIONS

This application is a continuation of U.S. patent application Ser. No.14/810,399 filed Jul. 27, 2015, which is a continuation of U.S. patentapplication Ser. No. 13/245,598, filed Sep. 26, 2011, both of which areincorporated herein by reference in their entirety.

COMPUTER PROGRAM LISTING APPENDIX

A computer program listing appendix is provided with this application.The computer program listing appendix is hereby incorporated byreference as if set forth in full in this application for all purposes.

BACKGROUND Field of the Invention

The present invention generally relates to electronic data and moreparticularly to data code creation on user devices.

Related Art

More and more consumers are purchasing items and services overelectronic networks such as, for example, the Internet. Consumersroutinely purchase products and services from merchants and individualsalike. The transactions may take place directly between a conventionalor on-line merchant or retailer and the consumer, and payment istypically made by entering credit card or other financial information.Transactions may also take place with the aid of an on-line or paymentprovider such as, for example, PayPal, Inc. of San Jose, Calif. Suchpayment providers can make transactions easier and safer for the partiesinvolved. Purchasing with the assistance of a payment provider from theconvenience of virtually anywhere using a mobile device is one mainreason why on-line and mobile payments are growing very quickly.Payments can be easily made through mobile apps created by individualsand companies, where a user can utilize the payment provider through theapp to make a payment for a service or item offered through the app.

However, with more and more sellers trying to take advantage of salesthrough a user's mobile device, there are many who do not know or havedifficulty creating the code necessary to allow a user to make purchasesthrough the app. This often involves trying to manually create code orhiring someone to create the code for payment portion of the app. Theformer can be difficult and time consumer, and the latter can be costly.

Therefore, it is desirable to allow a user to quickly and easily createcode to allow a payment through a mobile app.

SUMMARY

According to one embodiment, a user is presented with a first displaywith parties to a payment transaction and a second display on the samescreen, where the user can drag and drop the parties on the first screento the second screen to create a desired payment flow. A serviceprovider, such as a payment provider, builds code based on the paymentflow and zips it into a downloadable file. The user can then easilyimplement the zipped code into a mobile app that will allow a customerto make a purchase through the app using the payment provider.

The zipped code uses a library of payment options offered by the paymentprovider and allows the user to input custom variables into theseoptions. Code is automatically generated for the user to use based onthe user input.

In one embodiment, the first display includes a sender (e.g., thecustomer or payer), a primary recipient, and one or more secondaryrecipients. The user first drags a sender icon or image onto the seconddisplay. Any suitable combination of primary and secondary recipientscan also be dragged and dropped. If a particular drag and drop operationis prohibited, a screen may pop up or overlay informing the user thereasons why the action was not allowed. Once the user is satisfied withthe flow shown on the second display, the user may select a specifictype of device or operating system the code will reside on. In oneembodiment, the user can select from iOS code for an Apple iPhone, iPad,or iPod, Android code for Android platforms, and Blackberry code forBlackberry products. The appropriate code is generated and zipped, whichcan then be loaded into the user's app.

As a result, a user can quickly and easily introduce a desired paymentflow into a mobile app.

In other embodiments, different combinations of features or entities canbe shown on the first display to allow the user to generate codespecific to different payment scenarios.

These and other features and advantages of the present disclosure willbe more readily apparent from the detailed description of theembodiments set forth below taken in conjunction with the accompanyingfigures.

BRIEF DESCRIPTION OF THE FIGURES

FIG. 1 is a flowchart illustrating a method for the user to makepayments based on user location through a payment provider according toone embodiment;

FIGS. 2A-2F are exemplary screen shots a user sees in using the drag anddrop process of FIG. 1 to create a zipped payment process code for amobile app.; and

FIG. 3 is a block diagram of a networked system used in the paymentsystem described above according to one embodiment.

Embodiments of the present disclosure and their advantages are bestunderstood by referring to the detailed description that follows. Itshould be appreciated that like reference numerals are used to identifylike elements illustrated in one or more of the figures, whereinshowings therein are for purposes of illustrating embodiments of thepresent disclosure and not for purposes of limiting the same.

DETAILED DESCRIPTION

FIG. 1 is a flowchart illustrating an exemplary method 100 a serviceprovider performs to create and provide code to a user so that the usercan employ a payment process for customers to use on their mobiledevice. Service provider can be a payment provider, such as PayPal, Inc.of San Jose, Calif. At step 102, the payment provider provides the userwith an interface to allow the user to easily create a desired paymentflow. The interface may be provided on a user's computing device, suchas a PC, laptop, tablet, or smart phone, through any suitable means,such as a link or downloadable file. Once accessed, the interface, whichwill be described in more detail below, presents the user with twoscreens. The first screen instructs the user to drag and drop paymentflow “actors” onto the screen. The second screen instructs the user toselect payment actors from a list, which can be dragged and dropped fromthe second screen onto the first screen.

In this embodiment, there are three actors: a sender, a primaryreceiver, and a receiver. The sender is the party/person/entity sendingmoney, such as a buyer. The primary receiver is the party/person/entityreceiving the money from the sender. The receiver is theparty/person/entity receiving money from the primary receiver. Thisallows the user to set up payment flows for a simple payment, parallelpayments, or chained payments. A simple payment is a payment from thesender to a single receiver. A parallel payment is a payment from thesender to a plurality of receivers. A chained payment is from the senderto the primary receiver, who then sends all or a portion to one or morereceivers. In the current embodiment, the maximum number of receivers isthree, and only a single primary receiver is allowed. However, in otherembodiments, those numbers can vary, such as from two to six or morerecipients and more than one primary recipient. The number of types ofactors may also vary. For example, here there are three types of actors.However, in other embodiments, there may be four or more types.

Once the user is presented with the interface and screens, the userdrags a first actor (actor 1) from the second screen to the firstscreen. This communicates the action to the payment provider, whoreceives actor 1 at step 104. Actor 1 may be the sender, primaryrecipient, or a recipient. Attributes associated with actor 1 areconveyed to the payment provider, such as to a server managed by thepayment provider, through the user device.

At step 106, the payment provider determines whether actor 1 is asender. If actor 1 is not a sender, i.e., the user dragged the primaryreceiver or the receiver onto the first screen, actor 1 is not placed onthe first screen, and the payment provider notifies the user at step108. The notification can be on the interface, such as an overlay screenthat informs the user why the primary receiver or the receiver cannot beused in this step. After closing the overlay screen, the user may selectactor 1 again, where actor 1 is received by the payment provider at step104.

Once the received actor 1 is determined to properly be the sender, thesender is placed on the first screen, such as at the top or left side ofthe first screen. An arrow may be displayed, pointing outward from thesender, indicating the direction of the payment flow. The user thenselects a second actor (actor 2) from the second screen and drags anddrops actor 2 onto the first screen. The payment provider receivesinformation or attributes about actor 2 at step 110.

A determination is then made at step 112 whether actor 2 is a receiver.If not, e.g., the user selected a sender as actor 2, the user isnotified at step 114, such as through an overlay screen described above.The notification may inform the user why a sender is not an appropriateactor at this step. After closing the overlay screen, the user mayselect actor 2 again, where actor 2 is received by the payment providerat step 110.

Once the received actor 2 is determined to properly be a receiver offunds, a determination is made, at step 116, whether the receiver is aprimary receiver. If actor 2 is not a primary receiver, i.e., actor 2 isa secondary receiver (or just receiver), a determination is made at step118 whether the user is finished with the payment flow. If the user isfinished, the payment flow is a simple payment process in which a sendersends funds to a receiver. The receiver is placed on the first screen ofthe user interface at the end of the arrow, such that the user sees asender, an arrow pointing from the sender to the receiver, and thereceiver at the end of the arrow.

The determination at step 118 may include the payment provider receivinginformation from the user, such as through the interface on the userdevice, that the user has finished the payment flow. In one embodiment,the interface includes links, buttons, or icons associated with a typeof code for a mobile device. When the user selects a link, the paymentprovider knows that the user is finished and ready to have the codegenerated and provided. In another embodiment, the user may simplyselect a button or link that indicates “Done” or “Finished.”

Once finished, the payment provider generates and zips the appropriatecode at step 134. In one embodiment, the user selects the type ofappropriate code from the user interface. For example, types of codesavailable may include from iOS code for an Apple iPhone or iPad, Androidcode for Android platforms, and Blackberry code for Blackberry products.Once the type of code is determined by the user and received by thepayment provider, such as through the interface, the payment providergenerates the code.

The zipped code allows the user to implement the payment process on amobile device. Thus, the user may install the code, which will enable acustomer to make a purchase or payment on the customer's mobile devicewith the services of the payment provider. For example, a customer mayaccess a user's app on the customer's phone and make a payment with theflow created by the user.

At step 136, the zipped code is delivered to the user. For example, thepayment provider may present the user with a zipped folder of filesand/or documents on a screen of the user's device. The user may thenaccess the folder to install the code. The folder may also includedocumentation and/or manuals for use. In this example, the user hascreated a simple payment flow having one sender and one receiver.

Returning back to step 118, if it is determined that the user has notfinished with the desired payment flow, another actor is selected by theuser and received by the payment provider at step 120. Note that thenotation of actor 2 in the flowchart does not limit the selection to bethe second actor. It is meant simply to convey a continuation of thepayment flow from step 110.

Once received, the payment provider determines, at step 122, whether thereceived actor is proper. A proper actor at this stage of the paymentflow would be a receiver (not a primary receiver or a sender). If theselected and received actor is not proper, the user is notified at step124, where notification can be similar to the notifications at steps 108and 114 described above. Thus, the payment provider will allow the userto select and for the payment provider to receive additional receiversat step 120 until a maximum limit is reached. In this embodiment, thenumber is three; however more than three is also possible.

When finished or the maximum number reached, the payment providergenerates and zips the appropriate code (at step 134) and delivers thecode to the user (at step 136). Here, the user has created a parallelpayment flow having one sender and two or more recipients.

Returning back to step 116, if it is determined that the actor receivedfrom the user at step 110 is a primary receiver, the user next selects athird actor (actor 3) from the second screen of the interface. Thepayment provider receives the selection of actor 3 at step 126 anddetermines, at step 128, whether the received actor 3 is a primary actoror a sender (both improper actors at this stage of the flow). If so, theuser is notified, at step 130, that an improper actor has been selected.The user can then select again an actor from the second screen, which isreceived again by the payment provider at step 126.

If the received actor 3 is a proper actor (i.e., not a sender or aprimary recipient, but rather a recipient), a determination is made, atstep 132, whether the user is finished with the payment flow. At thisstage, the user has selected a sender, a primary recipient, and arecipient for a chained payment flow. If the user has finished, such asdetermined by the user selecting an appropriate link or button or by theuser selecting a type of code to generate, the code is generated andzipped at step 134 and delivered to the user at step 136. This thenallows the user to implement a chained payment flow with one sender, oneprimary recipient, and one recipient. This may be the case where thesender sends $100 to the primary recipient, who keeps $40 and sends $60to the recipient.

If, as determined at step 132, the user has not finished the desiredpayment flow, the user continues to select actors (which necessarilyhave to be recipients in this embodiment) until the desired or maximumnumber of recipients is reached. At that time, the payment providergenerates and zips the appropriate code, at step 134, for theuser-created payment flow and delivers the code to the user at step 136.The code thus delivered allows the user to implement a chained paymentflow with one sender, one primary recipient, and two or more recipients.For example, the sender can send $100 to the primary recipient, theprimary recipient keeps $20, and primary recipient sends $40 to a firstrecipient, $10 to a second recipient, and $30 to a third recipient.

As a result, a user is able to quickly and easily create a desiredpayment flow using a simple drag and drop process on a single screen.Code is automatically generated by the payment provider and provided tothe user for installation. The user can then accept payments through thepayment provider from customers on a mobile device.

FIGS. 2A-2F are exemplary screen shots a user sees in using the drag anddrop process of FIG. 1 to create a zipped payment process code for amobile app. In FIG. 2A, an interface 200 is provided by the paymentprovider on a computing device, such as a PC. Interface 200 includes afirst screen 202 and a second screen 204. First screen 202 is where theuser drags and drops actors for the desired payment flow. Second screen204 is where the actors are dragged from. Second screen includes, inthis embodiment, three actors, although more or less may be shown. Asender 206, a primary receiver 208, and a receiver (or secondaryreceiver) 201 are visually shown with an icon and text. The user canplace a mouse over the desired actor, click, hold, drag the actor tofirst screen 202, and release to drop the actor. Other ways of draggingand dropping or selecting may also be used. For example, the user mayclick on an actor, move the mouse, and click again. The user may alsoplace a pointer or finger on the desired actor and move the actor tofirst screen 202.

In FIG. 2B, the user has dragged and dropped sender 206 from secondscreen 204 onto first screen 202, where sender 206 is shown with anarrow 212 indicating a directional flow of funds from the sender. Thiscan be achieved by using JQuery open source code and HTML 5 drag anddrop functionality. Backend code is thus activated and a placeholder isplaced that will be used when the code samples are generated.

In FIG. 2C, the user has dragged and dropped primary receiver 208 fromsecond screen 204 onto first screen 202. The user can drop primaryreceiver 208 anywhere on first screen 202, and primary receiver 208 will“snap” to a desired position directly underneath arrow 212. An arrow 214is also displayed indicating a continued directional flow of funds. Thedragging and dropping activates the backend code and puts a placeholderthat will be used when the code samples are generated.

In this example, the user is creating a chained payment flow. If theuser wanted to create a simple payment flow or a parallel payment flow,the user would have dragged and dropped receiver 210, instead of primaryreceiver 208, after dragging and dropping sender 206.

In FIG. 2D, the user has dragged and dropped receiver 210 threesequential times from second screen 204 onto first screen 202. The usercan drop receiver 210 anywhere on first screen 202, and receiver 210will “snap” to a desired position underneath arrow 214. Receiver 210from second screen 204 is dropped three separate times onto first screen202 to display a first receiver 210-1, a second receiver 210-2, and athird receiver 210-3. The dragging and dropping activates the backendcode and puts a placeholder that will be used when the code samples aregenerated.

Also shown in FIG. 2D are three icons 216, 218, and 220, which representthree different types of code that can be generated, specific todifferent mobile devices or platforms. When icon 216 is selected by theuser, iOS code for an Apple iPad or iPhone can be generated. When icon218 is selected by the user, Android code for mobile devices using theAndroid platform, such as devices from LG, Samsung, HTC, Motorola, andSony, can be generated. When icon 220 is selected by the user,Blackberry code for use on Blackberry mobile devices can be generated.In other embodiments, more or less codes can be included as icons orlinks selectable by the user.

In FIG. 2E, the user has selected one of icons 216, 218, or 220,indicating to the payment provider that the user has finished thepayment flow, and a JQuery light box option overlay window 222 isopened. Within overlay window 222 are icons/links 224 for getting iOScode, 226 for getting Android code, and 228 for getting Blackberry code.This actions a payment provider server to check the placeholders thatwere selected previously and generate the code for that device based onthe mobile device option the user chose.

In FIG. 2F, the user has selected icon/link 224 to generate iOS code foran iPhone/iPad. The user is presented with a save dialog box 230 to savethe code to add to the user's mobile application. A zip file is createdand presented to the user (e.g., saved or opened) after the user selectsa desired option and the “OK” button. The user may then open the file toaccess documents and other data to add the code and implement thedesired payment flow. In another embodiment, dialog box 230 is notshown, and the zip file is created directly after the user selects anicon/link from overlay window 222 in FIG. 2E.

In an enterprise software environment, adding a middleman to softwaredevelopment and relying on any outside company for approval and usageterms drastically drains company resources, delays delivery dates, andlimits enhanced functionality. The process described above overcomesthis by utilizing HTML5, which is the new standard for enterprise andpersonal apps. This allows the payment provider to create a drag anddrop solution for merchants on and off line to easily implement apayment flow into their mobile apps.

The general solution can be easily changed to used in many differentareas. Some examples include at a point of sale (POS), at festival/showbooths, at small merchants/restaurants, and for digital contentproviders. At a POS, the drag and drop solution can be implemented inoutlets by changing the available options to choose color, add your ownlogo, choose layout style, payment provider branding options, and choiceof device to run the code on.

At festival/show booths, the drag and drop can be combined with the POSsolution to allow vendors to easily set up a payment system to sellgoods/services and receive payment through a mobile app. The vendorcould log onto the payment provider site and use the drag and dropinterface to choose the options and layouts the vendor wants, upload alogo, download the customized payment code, and upload the code to thevendor's mobile platform of choice. The vendor can then start acceptingpayments.

Smaller retailers/merchants can benefit by being able to incorporate apayment flow with a payment provider and utilize the services quickly,easily, and at very little cost on mobile apps.

With digital content providers, they could use the drag and dropinterface to create customized solutions for all their content needsusing the payment provider as a payment option.

Refer to the computer program listing appendix for a sample code for afront end breakdown and a backend breakdown. The sample code includesexplanatory notes shown between double brackets.

Backend PHP Code

A payment provider, such as PayPal, may allow developers to use itsMobile Payment Library (MPL), such as on x.com, PayPal's developerportal, to create various payment options. These contain files to beused in developer projects while building mobile applications.

An exemplary logic of the drag and drop tool is as follows:

Based on user selected preferences on the front end (drag and drop)functionality backend scripts (PHP programming language) areautomatically editing library project files with parameters provided bythe user. After all changes are made, a full set of required files isarchived (zipped) and provided for users to download. Here are theexamples of such functionality in the backend:

Changing file contents: <?php  $fname = “anyrequiredfile.txt”;  $exclude= “replaceable string”;  $lines = file($fname);  $out = “”;  foreach($lines as $line) { if (strstr($line, $exclude) == “”) {  $out .= $line;}  }  $f = fopen($fname, “w”);  fwrite($f, $out);  fclose($f); ?>

Archiving files and making them available to end users: <?php functioncreate_zip($files = array( ),$destination = “,$overwrite = false) {if(file_exists($destination) && !$overwrite) { return false; }$valid_files = array( ); if(is_array($files)) { foreach($files as $file){ if(file_exists($file)) { $valid_files[ ] = $file; } } }if(count($valid_files)) { $zip = new ZipArchive( ); if($zip−>open($destination,$overwrite ?  ZIPARCHIVE::OVERWRITE :ZIPARCHIVE::CREATE) !== true) { return false;  }  //add the files foreach($valid_files as $file) { $zip−>addFile($file,$file);  } $zip->close( );  //check to make sure the file exists  returnfile_exists($destination);  }  else  {  return false;  } }?>

This technology allows for various applications to be developed wherefile content can be customized according to GUI changes a user makes byusing the drag and drop interface described herein.

FIG. 3 is a block diagram of a computer system 300 suitable forimplementing, for example, devices used in the process described herein,including user and payment provider devices.

In accordance with various embodiments of the present disclosure,computer system 300, such as a computer and/or a network server,includes a bus 302 or other communication mechanism for communicatinginformation, which interconnects subsystems and components, such as aprocessing component 304 (e.g., processor, micro-controller, digitalsignal processor (DSP), etc.), a system memory component 306 (e.g.,RAM), a static storage component 308 (e.g., ROM), a disk drive component310 (e.g., magnetic or optical), a network interface component 312(e.g., modem or Ethernet card), a display component 314 (e.g., CRT orLCD), an input component 318 (e.g., keyboard, keypad, or virtualkeyboard), a cursor control component 320 (e.g., mouse, pointer, ortrackball), and/or a location determination component 322 (e.g., aGlobal Positioning System (GPS), a cell tower triangulation device,and/or a variety of other location determination devices known in theart). In one implementation, disk drive component 310 may comprise adatabase having one or more disk drive components.

In accordance with embodiments of the present disclosure, computersystem 300 performs specific operations by processor 304 executing oneor more sequences of instructions contained in memory component 306,such as described herein with respect to the user device and/or thepayment provider device. Such instructions may be read into systemmemory component 306 from another computer readable medium, such asstatic storage component 308 or disk drive component 310. In otherembodiments, hard-wired circuitry may be used in place of or incombination with software instructions to implement the presentdisclosure.

Logic may be encoded in a computer readable medium, which may refer toany medium that participates in providing instructions to processor 304for execution. Such a medium may take many forms, including but notlimited to, non-volatile media, volatile media, and transmission media.In one embodiment, the computer readable medium is non-transitory. Invarious implementations, non-volatile media includes optical or magneticdisks, such as disk drive component 310, volatile media includes dynamicmemory, such as system memory component 306, and transmission mediaincludes coaxial cables, copper wire, and fiber optics, including wiresthat comprise bus 302. In one example, transmission media may take theform of acoustic or light waves, such as those generated during radiowave and infrared data communications.

Some common forms of computer readable media includes, for example,floppy disk, flexible disk, hard disk, magnetic tape, any other magneticmedium, CD-ROM, any other optical medium, punch cards, paper tape, anyother physical medium with patterns of holes, RAM, PROM, EPROM,FLASH-EPROM, any other memory chip or cartridge, carrier wave, or anyother medium from which a computer is adapted to read. In oneembodiment, the computer readable media is non-transitory.

In various embodiments of the present disclosure, execution ofinstruction sequences to practice the present disclosure may beperformed by computer system 300. In various other embodiments of thepresent disclosure, a plurality of computer systems 300 coupled by acommunication link 324 to network 310 (e.g., such as a LAN, WLAN, PTSN,and/or various other wired or wireless networks, includingtelecommunications, mobile, and cellular phone networks) may performinstruction sequences to practice the present disclosure in coordinationwith one another.

Computer system 300 may transmit and receive messages, data, informationand instructions, including one or more programs (i.e., applicationcode) through communication link 324 and network interface component312. Network interface component 312 may include an antenna, eitherseparate or integrated, to enable transmission and reception viacommunication link 324. Received program code may be executed byprocessor 304 as received and/or stored in disk drive component 310 orsome other non-volatile storage component for execution.

Where applicable, various embodiments provided by the present disclosuremay be implemented using hardware, software, or combinations of hardwareand software. Also, where applicable, the various hardware componentsand/or software components set forth herein may be combined intocomposite components comprising software, hardware, and/or both withoutdeparting from the scope of the present disclosure. Where applicable,the various hardware components and/or software components set forthherein may be separated into sub-components comprising software,hardware, or both without departing from the scope of the presentdisclosure. In addition, where applicable, it is contemplated thatsoftware components may be implemented as hardware components andvice-versa.

Software, in accordance with the present disclosure, such as programcode and/or data, may be stored on one or more computer readablemediums. It is also contemplated that software identified herein may beimplemented using one or more general purpose or specific purposecomputers and/or computer systems, networked and/or otherwise. Whereapplicable, the ordering of various steps described herein may bechanged, combined into composite steps, and/or separated into sub-stepsto provide features described herein.

The foregoing disclosure is not intended to limit the present disclosureto the precise forms or particular fields of use disclosed. As such, itis contemplated that various alternate embodiments and/or modificationsto the present disclosure, whether explicitly described or impliedherein, are possible in light of the disclosure. Having thus describedembodiments of the present disclosure, persons of ordinary skill in theart will recognize that changes may be made in form and detail withoutdeparting from the scope of the present disclosure. Thus, the presentdisclosure is limited only by the claims.

What is claimed is:
 1. A device, comprising: a display componentconfigured to execute touchscreen functionality code, wherein thetouchscreen functionality code is based on a mobile app version of ahypertext mark-up language; a touchscreen interface configured toperform the following operations based at least on the touchscreenfunctionality code executed: receive a first touch-sense inputresponsive to movement of a first graphic icon from a first input areaof the touchscreen interface to a second input area of the touchscreeninterface, wherein the first graphic icon represents a first actor;receive a second touch-sense input responsive to movement of a secondgraphic icon from the first input area to the second input area, whereinthe second graphic icon represents a second actor; and receive a thirdtouch-sense input responsive to a selection on the touchscreen interfacethat indicates a type of computer code; a processing componentconfigured to request an execution of backend code based at least on thefirst touch-sense input, the second touch-sense input, and the thirdtouch-sense input; and a network interface antenna configured to receivenetwork-flow code based at least on the execution of the backend code,and wherein the network-flow code enables the device to perform actionsin a network flow associated with the first actor and the second actor.2. The device of claim 1, wherein the touchscreen functionality codecomprises a j query plugin that configures the touchscreen interface toreceive the first touch-sense input, the second touch-sense input, andthe third touch-sense input.
 3. The device of claim 1, wherein themovement of the first graphic icon from the first input area of thetouchscreen interface to the second input area of the touchscreeninterface comprises a first drag-and-drop movement on a surface of thetouchscreen interface, and wherein the movement of the second graphicicon from the first input area to the second input area of thetouchscreen interface comprises a second drag-and drop movement on thesurface of the touchscreen interface.
 4. The device of claim 1, whereinthe network flow comprises at least one of a simple network flowassociated with at least the first actor and the second actor, aparallel network flow associated with at least the first actor and thesecond actor, and a chained network flow associated with at least thefirst actor and the second actor, wherein the chained network flowcomprises one or more additional network flows to one or more additionalactors.
 5. The device of claim 4, wherein at least one of the firstactor and the second actor comprises a network flow sender, and whereinthe one or more additional actors comprise a network flow recipient. 6.The device of claim 1, wherein the network flow code is downloadable bythe device, and wherein the device is configured to perform the actionsin the network flow based on the network flow code downloaded.
 7. Amethod, comprising: executing, by a mobile device comprising one or morehardware processors, touchscreen functionality code, wherein thetouchscreen functionality code is based on a mobile app version of ahypertext mark-up language; receiving, via a touchscreen interface ofthe mobile device, a first touch-sense input responsive to movement of afirst graphic icon from a first input area of the touchscreen interfaceto a second input area of the touchscreen interface, wherein the firstgraphic icon represents a first actor; receiving, via the touchscreeninterface, a second touch-sense input responsive to movement of a secondgraphic icon from the first input area to the second input area, whereinthe second graphic icon represents a second actor; receiving, via thetouchscreen interface, a third touch-sense input responsive to aselection on the touchscreen interface that indicates a type of computercode; transmitting a request for an execution of backend code based atleast on the first touch-sense input, the second touch-sense input, andthe third touch-sense input; and subsequent to the transmitting,receiving network-flow code based at least on the execution of thebackend code, and wherein the network-flow code enables the mobiledevice to perform actions in a network flow associated with the firstactor and the second actor.
 8. The method of claim 7, wherein thetouchscreen functionality code comprises a j query plugin thatconfigures the touchscreen interface to receive the first touch-senseinput, the second touch-sense input, and the third touch-sense input. 9.The method of claim 7, wherein the movement of the first graphic iconfrom the first input area of the touchscreen interface to the secondinput area of the touchscreen interface comprises a first drag-and-dropmovement on a surface of the touchscreen interface, and wherein themovement of the second graphic icon from the first input area to thesecond input area of the touchscreen interface comprises a seconddrag-and drop movement on the surface of the touchscreen interface. 10.The method of claim 7, wherein the network flow comprises at least oneof a simple network flow associated with at least the first actor andthe second actor, a parallel network flow associated with at least thefirst actor and the second actor, and a chained network flow associatedwith at least the first actor and the second actor.
 11. The method ofclaim 10, wherein the chained network flow comprises one or moreadditional network flows to one or more additional actors.
 12. Themethod of claim 10, wherein at least one of the first actor and thesecond actor comprises a network flow sender, and wherein the one ormore additional actors comprise a network flow recipient.
 13. The methodof claim 7, wherein the network flow code is downloadable by the mobiledevice, and wherein the mobile device is configured to perform theactions in the network flow based on the network flow code downloaded.14. A non-transitory computer readable medium storingcomputer-executable instructions that in response to execution by one ormore hardware processors, causes a device to perform operationscomprising: executing, by a mobile device comprising one or morehardware processors, touchscreen functionality code, wherein thetouchscreen functionality code is based on a mobile app version of ahypertext mark-up language; receiving, via a touchscreen interface ofthe mobile device, a first touch-sense input responsive to movement of afirst graphic icon from a first input area of the touchscreen interfaceto a second input area of the touchscreen interface, wherein the firstgraphic icon represents a first actor; receiving, via the touchscreeninterface, a second touch-sense input responsive to movement of a secondgraphic icon from the first input area to the second input area, whereinthe second graphic icon represents a second actor; receiving, via thetouchscreen interface, a third touch-sense input responsive to aselection on the touchscreen interface that indicates a type of computercode; transmitting a request for an execution of backend code based atleast on the first touch-sense input, the second touch-sense input, andthe third touch-sense input; and subsequent to the transmitting,receiving network-flow code based at least on the execution of thebackend code, and wherein the network-flow code enables the mobiledevice to perform actions in a network flow associated with the firstactor and the second actor.
 15. The non-transitory computer readablemedium of claim 14, wherein the touchscreen functionality code comprisesa j query plugin that configures the touchscreen interface to receivethe first touch-sense input, the second touch-sense input, and the thirdtouch-sense input.
 16. The non-transitory computer readable medium ofclaim 14, wherein the movement of the first graphic icon from the firstinput area of the touchscreen interface to the second input area of thetouchscreen interface comprises a first drag-and-drop movement on asurface of the touchscreen interface, and wherein the movement of thesecond graphic icon from the first input area to the second input areaof the touchscreen interface comprises a second drag-and drop movementon the surface of the touchscreen interface.
 17. The non-transitorycomputer readable medium of claim 14, wherein the network flow comprisesat least one of a simple network flow associated with at least the firstactor and the second actor, a parallel network flow associated with atleast the first actor and the second actor, and a chained network flowassociated with at least the first actor and the second actor.
 18. Thenon-transitory computer readable medium of claim 17, wherein the chainednetwork flow comprises one or more additional network flows to one ormore additional actors.
 19. The non-transitory computer readable mediumof claim 17, wherein at least one of the first actor and the secondactor comprises a network flow sender, and wherein the one or moreadditional actors comprise a network flow recipient.
 20. Thenon-transitory computer readable medium of claim 14, wherein the networkflow code is downloadable by the mobile device, and wherein the mobiledevice is configured to perform the actions in the network flow based onthe network flow code downloaded.